Slide 1
Web Accessibility Analytics and Open Source Tools for Inspecting and Auditing Web Resources for Accessibility
The Session begins at 1:00 pm CST
We will be testing audio quality periodically
Slide 2 
Listening to the Webinar
•	The audio for today’s webinar is being broadcast through your computer. Please make sure your speakers are turned on or your headphones are plugged in.
•	You can control the audio broadcast via the Audio & Video panel.  You can adjust the sound by “sliding” the sound bar left or right.
•	If you are having sound quality problems check your audio controls by going through the Audio Wizard which is accessed by selecting the microphone icon on the Audio & Video panel 
Slide 3
Listening to the Webinar, continued
If you do not have sound capabilities on your computer or prefer to listen by phone, dial:
1-712-432-3066
Pass Code: 
148937
This is not a Toll Free number
Slide 4
Listening to the Webinar, continued
MOBILE Devices supported include iPhone, iPad, Android Devices, Kindle Fire HD)** 
	Individuals can download the free Blackboard Collaborate App from the Apple Store, Google Play or Amazon
  
Slide 5 
Captioning
•	Real-time captioning is provided during this webinar.
•	The caption screen can be accessed by choosing the     icon in the Audio & Video panel.
•	Once selected you will have the option to resize the captioning window, change the font size and save the transcript.
Slide 6
Submitting Questions
•	You may type and submit questions in the Chat Area Text Box or press Control-M and enter text in the Chat Area
•	If you are connected via a mobile device you may submit questions in the chat area within                                                                                  the App                                                                                                       
•	If you are listening by phone and not logged in to                                                                                              he webinar, you may ask questions by emailing                                                                                                      them to webinars@ada-audio.org
•	Please note: This webinar is being recorded and can be accessed on the website at www.ada-audio.org within 24 hours after the conclusion of the session.
Slide 7 
Customize Your View
•	Resize the Whiteboard where the Presentation slides are shown to make it smaller or larger by choosing from the drop down menu located above and to the left of the whiteboard.   The default is “fit page”
Slide 8
Customize Your View continued
•	Resize/Reposition the Chat, Participant and Audio & Video panels by “detaching” and using your mouse to reposition or “stretch/shrink”.  Each panel may be detached using the       icon in the upper right corner of each panel.
Slide 9
Setting Preferences
•	Depending on your system settings you may receive visual and audible notifications when individuals enter/leave the webinar room or when other actions are taken by participants.  This can be distracting.
•	To turn off notifications (audible/visual)
◦	Select “Edit” from the tool bar at the top of your screen
◦	From the drop down menu select “Preferences”
◦	Scroll down to “General”
•	select “Audible Notifications”   Uncheck anything you don’t want to receive and “apply”
•	Select “Visual Notifications” Uncheck anything you don’t want to receive and “apply”
◦	For Screen Reader User – Set preferences through the setting options within the Activity Window (Ctrl+slash opens the activity window)
Slide 10
Technical Assistance
•	If you experience any technical difficulties during the webinar:
◦	Submit a message regarding your issue via the chat area and the Moderator will address your concern via a private chat with you and/or refer it to one of the Great Lakes ADA Center IT Staff to contact you off line; or 
◦	Email webinars@ada-audio.org; or
◦	Call 877-232-1990 (V/TTY) 
Slide 11
Web Accessibility Analytics and Open Source Tools for Inspecting and Auditing Web Resources for Accessibility
•	By Jon Gunderson University of Illinois
Slide 12
Slides Available for Download
Slides at:
http://presentations.cita.illinois.edu/2014-04-29-webcon/ 
Slide 13
Overview
•	W3C Standards for Web Accessibility
•	OAA Rulesets
•	Getting Started
•	AInspector Sidebar
•	FAE 2.0 Testing Server
•	Next Steps
Slide 14
Web Content Accessibility Guidelines 2.0
screenshot of WCAG 2.0 
Slide 15
Accessible Rich Internet Applications (ARIA) 1.0
Screenshot of ARIA 1.0
Slide 16
HTML 5
Screenshot of HTML 5 in W3C 
Slide 17
HTML 5: main element
4.4.14 The main element
Categories:
    Flow content.
    Palpable content.
Contexts in which this element can be used:
    Where flow content is expected, but with no article, aside, footer, header or nav element ancestors.
Content model:
    Flow content.
Content attributes:
    Global attributes
Tag omission in text/html:
    Neither tag is omissible
Allowed ARIA role attribute values:
    main role (default - do not set) or presentation.
Allowed ARIA state and property attributes:
    Global aria-* attributes
    Any aria-* attributes applicable to the allowed roles.
DOM interface:
    Uses HTMLElement 
The main element represents the main content of the body of a document or application. The main content area consists of content that is directly related to or expands upon the central topic of a document or central functionality of an application.
Slide 18
OpenAjax Evaluation Library Rulesets
OAA Ruleset: WCAG + HTML5 + ARIA by Rule Category
Ruleset: WCAG + HTML5 + ARIA by Rule Category
Ruleset View Options
    Rule Categories
    WCAG 2.0 Guidelines
About Options
    Overview
    Rulesets
    Usage Statistics
    Concepts and Terms
    Disclaimer
    Version History
    Contact
Ruleset Title
WCAG 2.0 Level A and AA requirements using semantics and accessibility features HTML5 and ARIA 1.0
Version
0.9.4 Beta
Author
OpenAjax Accessibility Working Group
Description
Slide 19
Getting Started: Conceptual Foundation
Basic Concepts
Rule
    A low-level accessibility compliance requirement with numerous components, the most basic of which are a definition, an evaluation function, and result messages. When a rule is evaluated, it is assigned a rule result value.
Target resources
    The set of HTML elements to which a particular rule applies. These include familiar elements such as div, img and input, as well as a pseudo-element designated as page, which is a placeholder for the document element. When a rule is evaluated, each of its target resources is assigned an element result value.
Ruleset
    A set of rules that embodies specific standards compliance goals. Each rule within a ruleset is designated as either required or recommended, according to its relationship to the compliance goals of the ruleset.
Evaluation
    The application of all evaluation functions of all rules in the selected ruleset to their corresponding target resources in a web page, and the subsequent collection of all evaluation results and messages, at both the rule and element levels, into a dataset.
Rule result
    The aggregate result of a rule evaluation with respect to its target resources (all of its target elements and/or the entire page).
Element result
    The result of a rule evaluation with respect to one of its target elements. 
Slide 20
Basic Concepts – Objects
Chart description
Chart of 
Rule 
-Definition
-Evaluate function
-Result messages
-techniques
-other properties
Target Resources 
-HTML elements of page
Ruleset
-Each rule in a particular ruleset in designate as either required or recommended
Slide 21
Basic Concepts – Actions
Chart description
Ruleset 
Calls the evaluative function for each rule, which in turn examines the target resources on the page and assigns result values to elements and to the rule itself.
Page 
-Element Results
-Rule Results
-Summary Results
Results Values
Violation
Warning
Manual Check
Pass
Not Applicable 
Not Application
Hidden
Slide 22
Demonstration: AInspector Sidebar for Firefox
Get latest version of AInspector Sidebar from IT Access Website
•	Update your version of Firefox to the latest version to ensure compatibility
•	Analyzing current web page DOM for accessibility features
•	Organizes rules by Rule Categories and WCAG Guidelines
•	Map rules to WCAG 2.0 Single A and AA requirements
•	Highlighting element information
Slide 23
Accessible Web Coding Practices
Accessible Web Coding Practices
Slide 24
ARIA Resources
•	ARIA Specifications 
•	ARIA 1.0 Authoring Practices 
•	Landmark Example: DRES Website 
•	Widget Examples 
•	Dojo Toolkit Accessibility Support 
•	JQuery UI widgets that are accessible using ARIA 
•	JQuery UI Accessible demos 
Slide 25
Next Steps
•	Finish rules for WCAG 2.0 evaluation (10-12 more rules)
•	Testing validity of rules
•	Improving the rule messaging and references
•	User testing
•	Coding Practices: Design principles, resources and examples for each rule
•	FAE Auditor (new tool): Campus wide evaluation of web resources
Slide 26
Feature Prioritization
AInspector Sidebar Features
•	HTML Reports of evaluation results
•	Delayed, timed or event triggered re-evaluations of web page
•	Provide Manual Checking views
•	Additional accessibility information in highlighted elements
FAE 2.0 Features
•	Shibboleth authentication support
•	Rule rating and commenting within FAE 2.0
•	Analyzing password protected websites
•	Report annotation
Slide 27
Acknowledgements
Sponsors
•	University of Illinois
•	CIOs of the Committee on Institutional Cooperation (CIC)
•	IBM Corporation (OAA Evaluation Library and AInspector for Firebug)
Slide 28
Acknowledgements – Page 2
Primary Developers
•	Jon Gunderson, Illinois Project coordinator OAA evaluation library software development Software developer for FAE 2.0 
•	Nicholas Hoyt, Illinois Conceptual model for accessibility evaluation Interaction designer for AInspector and FAE 2.0 software developer for AInspector Sidebar 
•	Garrett Smith, Wisconsin Software development for FAE 2.0 
Slide 29
Acknowledgements – Page 3
Major Contributing Developers
•	Prasanna Bale, CITES Software developer for AInspector Firebug 
•	Pramod Joshi, AITS Software developer for fae-util 
•	Jeff Heckel, AITS Software developer for fae-util 
Slide 30
You Can Help
Open source and community development to meet the accessibility needs of developers and designers
•	Providing feedback on rules
•	Editing rule messaging
•	Identifying useful support resources that you use
•	Developing supporting documentation and tutorials
•	Developing coding practice examples
•	Contributing to coding of tools
Slide 31
Questions and Comments
Jon Gunderson
Division of Disability Resources and Educational Services
University of Illinois
jongund@illinois.edu 
Slide 32
Thank you for participating!
Next Session is July 24, 2014
High Quality Apps for Accessibility
The session today was recorded 
and will be archived at 
http://ada-audio.org/Archives/AccessibleTech/